SGI Freeware 2002 November

home *** CD-ROM | disk | FTP | other *** search

/ SGI Freeware 2002 November / SGI Freeware 2002 November - Disc 2.iso / dist / fw_grep.idb / usr / freeware / catman / u_man / cat1 / grep.Z / grep

Wrap

Text File | 2000-04-13 | 28KB | 529 lines

GGGGRRRREEEEPPPP((((1111)))) GGGGNNNNUUUU PPPPrrrroooojjjjeeeecccctttt ((((2222000000000000////00002222////22226666)))) GGGGRRRREEEEPPPP((((1111)))) NNNNAAAAMMMMEEEE grep, egrep, fgrep - print lines matching a pattern SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS ggggrrrreeeepppp [_o_p_t_i_o_n_s] _P_A_T_T_E_R_N [_F_I_L_E...] ggggrrrreeeepppp [_o_p_t_i_o_n_s] [----eeee _P_A_T_T_E_R_N | ----ffff _F_I_L_E] [_F_I_L_E...] DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN GGGGrrrreeeepppp searches the named input _F_I_L_Es (or standard input if no files are named, or the file name ---- is given) for lines containing a match to the given _P_A_T_T_E_R_N. By default, ggggrrrreeeepppp prints the matching lines. In addition, two variant programs eeeeggggrrrreeeepppp and ffffggggrrrreeeepppp are available. EEEEggggrrrreeeepppp is the same as ggggrrrreeeepppp ----EEEE. FFFFggggrrrreeeepppp is the same as ggggrrrreeeepppp ----FFFF. OOOOPPPPTTTTIIIIOOOONNNNSSSS ----AAAA _N_U_M, --------aaaafffftttteeeerrrr----ccccoooonnnntttteeeexxxxtttt====_N_U_M Print _N_U_M lines of trailing context after matching lines. ----aaaa, --------tttteeeexxxxtttt Process a binary file as if it were text; this is equivalent to the --------bbbbiiiinnnnaaaarrrryyyy----ffffiiiilllleeeessss====tttteeeexxxxtttt option. ----BBBB _N_U_M, --------bbbbeeeeffffoooorrrreeee----ccccoooonnnntttteeeexxxxtttt====_N_U_M Print _N_U_M lines of leading context before matching lines. ----CCCC [_N_U_M], ----_N_U_M, --------ccccoooonnnntttteeeexxxxtttt[====_N_U_M] Print _N_U_M lines (default 2) of output context. ----bbbb, --------bbbbyyyytttteeee----ooooffffffffsssseeeetttt Print the byte offset within the input file before each line of output. --------bbbbiiiinnnnaaaarrrryyyy----ffffiiiilllleeeessss====_T_Y_P_E If the first few bytes of a file indicate that the file contains binary data, assume that the file is of type _T_Y_P_E. By default, _T_Y_P_E is bbbbiiiinnnnaaaarrrryyyy, and ggggrrrreeeepppp normally outputs either a one-line message saying that a binary file matches, or no message if there is no match. If _T_Y_P_E is wwwwiiiitttthhhhoooouuuutttt----mmmmaaaattttcccchhhh, ggggrrrreeeepppp assumes that a binary file does not match; this is equivalent to the ----IIII option. If _T_Y_P_E is tttteeeexxxxtttt, ggggrrrreeeepppp processes a binary file as if it were text; this is equivalent to the ----aaaa option. _W_a_r_n_i_n_g: ggggrrrreeeepppp --------bbbbiiiinnnnaaaarrrryyyy----ffffiiiilllleeeessss====tttteeeexxxxtttt might output binary garbage, which can have nasty side effects if the output is a terminal and if the terminal driver interprets some of it as commands. Page 1 (printed 4/5/00) GGGGRRRREEEEPPPP((((1111)))) GGGGNNNNUUUU PPPPrrrroooojjjjeeeecccctttt ((((2222000000000000////00002222////22226666)))) GGGGRRRREEEEPPPP((((1111)))) ----cccc, --------ccccoooouuuunnnntttt Suppress normal output; instead print a count of matching lines for each input file. With the ----vvvv, --------iiiinnnnvvvveeeerrrrtttt----mmmmaaaattttcccchhhh option (see below), count non-matching lines. ----dddd _A_C_T_I_O_N, --------ddddiiiirrrreeeeccccttttoooorrrriiiieeeessss====_A_C_T_I_O_N If an input file is a directory, use _A_C_T_I_O_N to process it. By default, _A_C_T_I_O_N is rrrreeeeaaaadddd, which means that directories are read just as if they were ordinary files. If _A_C_T_I_O_N is sssskkkkiiiipppp, directories are silently skipped. If _A_C_T_I_O_N is rrrreeeeccccuuuurrrrsssseeee, ggggrrrreeeepppp reads all files under each directory, recursively; this is equivalent to the ----rrrr option. ----EEEE, --------eeeexxxxtttteeeennnnddddeeeedddd----rrrreeeeggggeeeexxxxpppp Interpret _P_A_T_T_E_R_N as an extended regular expression (see below). ----eeee _P_A_T_T_E_R_N, --------rrrreeeeggggeeeexxxxpppp====_P_A_T_T_E_R_N Use _P_A_T_T_E_R_N as the pattern; useful to protect patterns beginning with ----. ----FFFF, --------ffffiiiixxxxeeeedddd----ssssttttrrrriiiinnnnggggssss Interpret _P_A_T_T_E_R_N as a list of fixed strings, separated by newlines, any of which is to be matched. ----ffff _F_I_L_E, --------ffffiiiilllleeee====_F_I_L_E Obtain patterns from _F_I_L_E, one per line. The empty file contains zero patterns, and therefore matches nothing. ----GGGG, --------bbbbaaaassssiiiicccc----rrrreeeeggggeeeexxxxpppp Interpret _P_A_T_T_E_R_N as a basic regular expression (see below). This is the default. ----HHHH, --------wwwwiiiitttthhhh----ffffiiiilllleeeennnnaaaammmmeeee Print the filename for each match. ----hhhh, --------nnnnoooo----ffffiiiilllleeeennnnaaaammmmeeee Suppress the prefixing of filenames on output when multiple files are searched. --------hhhheeeellllpppp Output a brief help message. ----IIII Process a binary file as if it did not contain matching data; this is equivalent to the --------bbbbiiiinnnnaaaarrrryyyy---- ffffiiiilllleeeessss====wwwwiiiitttthhhhoooouuuutttt----mmmmaaaattttcccchhhh option. ----iiii, --------iiiiggggnnnnoooorrrreeee----ccccaaaasssseeee Ignore case distinctions in both the _P_A_T_T_E_R_N and the Page 2 (printed 4/5/00) GGGGRRRREEEEPPPP((((1111)))) GGGGNNNNUUUU PPPPrrrroooojjjjeeeecccctttt ((((2222000000000000////00002222////22226666)))) GGGGRRRREEEEPPPP((((1111)))) input files. ----LLLL, --------ffffiiiilllleeeessss----wwwwiiiitttthhhhoooouuuutttt----mmmmaaaattttcccchhhh Suppress normal output; instead print the name of each input file from which no output would normally have been printed. The scanning will stop on the first match. ----llll, --------ffffiiiilllleeeessss----wwwwiiiitttthhhh----mmmmaaaattttcccchhhheeeessss Suppress normal output; instead print the name of each input file from which output would normally have been printed. The scanning will stop on the first match. --------mmmmmmmmaaaapppp If possible, use the mmmmmmmmaaaapppp(2) system call to read input, instead of the default rrrreeeeaaaadddd(2) system call. In some situations, --------mmmmmmmmaaaapppp yields better performance. However, --------mmmmmmmmaaaapppp can cause undefined behavior (including core dumps) if an input file shrinks while ggggrrrreeeepppp is operating, or if an I/O error occurs. ----nnnn, --------lllliiiinnnneeee----nnnnuuuummmmbbbbeeeerrrr Prefix each line of output with the line number within its input file. ----qqqq, --------qqqquuuuiiiieeeetttt, --------ssssiiiilllleeeennnntttt Quiet; suppress normal output. The scanning will stop on the first match. Also see the ----ssss or --------nnnnoooo----mmmmeeeessssssssaaaaggggeeeessss option below. ----rrrr, --------rrrreeeeccccuuuurrrrssssiiiivvvveeee Read all files under each directory, recursively; this is equivalent to the ----dddd rrrreeeeccccuuuurrrrsssseeee option. ----ssss, --------nnnnoooo----mmmmeeeessssssssaaaaggggeeeessss Suppress error messages about nonexistent or unreadable files. Portability note: unlike GNU ggggrrrreeeepppp, traditional ggggrrrreeeepppp did not conform to POSIX.2, because traditional ggggrrrreeeepppp lacked a ----qqqq option and its ----ssss option behaved like GNU ggggrrrreeeepppp's ----qqqq option. Shell scripts intended to be portable to traditional ggggrrrreeeepppp should avoid both ----qqqq and ----ssss and should redirect output to /dev/null instead. ----UUUU, --------bbbbiiiinnnnaaaarrrryyyy Treat the file(s) as binary. By default, under MS-DOS and MS-Windows, ggggrrrreeeepppp guesses the file type by looking at the contents of the first 32KB read from the file. If ggggrrrreeeepppp decides the file is a text file, it strips the CR characters from the original file contents (to make regular expressions with ^^^^ and $$$$ work correctly). Specifying ----UUUU overrules this guesswork, causing all files to be read and passed to the matching mechanism Page 3 (printed 4/5/00) GGGGRRRREEEEPPPP((((1111)))) GGGGNNNNUUUU PPPPrrrroooojjjjeeeecccctttt ((((2222000000000000////00002222////22226666)))) GGGGRRRREEEEPPPP((((1111)))) verbatim; if the file is a text file with CR/LF pairs at the end of each line, this will cause some regular expressions to fail. This option has no effect on platforms other than MS-DOS and MS-Windows. ----uuuu, --------uuuunnnniiiixxxx----bbbbyyyytttteeee----ooooffffffffsssseeeettttssss Report Unix-style byte offsets. This switch causes ggggrrrreeeepppp to report byte offsets as if the file were Unix- style text file, i.e. with CR characters stripped off. This will produce results identical to running ggggrrrreeeepppp on a Unix machine. This option has no effect unless ----bbbb option is also used; it has no effect on platforms other than MS-DOS and MS-Windows. ----VVVV, --------vvvveeeerrrrssssiiiioooonnnn Print the version number of ggggrrrreeeepppp to standard error. This version number should be included in all bug reports (see below). ----vvvv, --------iiiinnnnvvvveeeerrrrtttt----mmmmaaaattttcccchhhh Invert the sense of matching, to select non-matching lines. ----wwww, --------wwwwoooorrrrdddd----rrrreeeeggggeeeexxxxpppp Select only those lines containing matches that form whole words. The test is that the matching substring must either be at the beginning of the line, or preceded by a non-word constituent character. Similarly, it must be either at the end of the line or followed by a non-word constituent character. Word- constituent characters are letters, digits, and the underscore. ----xxxx, --------lllliiiinnnneeee----rrrreeeeggggeeeexxxxpppp Select only those matches that exactly match the whole line. ----yyyy Obsolete synonym for ----iiii. ----ZZZZ, --------nnnnuuuullllllll Output a zero byte (the ASCII NNNNUUUULLLL character) instead of the character that normally follows a file name. For example, ggggrrrreeeepppp ----llllZZZZ outputs a zero byte after each file name instead of the usual newline. This option makes the output unambiguous, even in the presence of file names containing unusual characters like newlines. This option can be used with commands like ffffiiiinnnndddd ----pppprrrriiiinnnntttt0000, ppppeeeerrrrllll ----0000, ssssoooorrrrtttt ----zzzz, and xxxxaaaarrrrggggssss ----0000 to process arbitrary file names, even those that contain newline characters. RRRREEEEGGGGUUUULLLLAAAARRRR EEEEXXXXPPPPRRRREEEESSSSSSSSIIIIOOOONNNNSSSS PPPPaaaaggggeeee 4444 ((((pppprrrriiiinnnntttteeeedddd 4444////5555////00000000)))) GGGGRRRREEEEPPPP((((1111)))) GGGGNNNNUUUU PPPPrrrroooojjjjeeeecccctttt ((((2222000000000000////00002222////22226666)))) GGGGRRRREEEEPPPP((((1111)))) A regular expression is a pattern that describes a set of strings. Regular expressions are constructed analogously to arithmetic expressions, by using various operators to combine smaller expressions. GGGGrrrreeeepppp understands two different versions of regular expression syntax: ``basic'' and ``extended.'' In GNU ggggrrrreeeepppp, there is no difference in available functionality using either syntax. In other implementations, basic regular expressions are less powerful. The following description applies to extended regular expressions; differences for basic regular expressions are summarized afterwards. The fundamental building blocks are the regular expressions that match a single character. Most characters, including all letters and digits, are regular expressions that match themselves. Any metacharacter with special meaning may be quoted by preceding it with a backslash. A list of characters enclosed by [[[[ and ]]]] matches any single character in that list; if the first character of the list is the caret ^^^^ then it matches any character _n_o_t in the list. For example, the regular expression [[[[0000111122223333444455556666777788889999]]]] matches any single digit. A range of characters may be specified by giving the first and last characters, separated by a hyphen. Finally, certain named classes of characters are predefined. Their names are self explanatory, and they are [[[[::::aaaallllnnnnuuuummmm::::]]]], [[[[::::aaaallllpppphhhhaaaa::::]]]], [[[[::::ccccnnnnttttrrrrllll::::]]]], [[[[::::ddddiiiiggggiiiitttt::::]]]], [[[[::::ggggrrrraaaapppphhhh::::]]]], [[[[::::lllloooowwwweeeerrrr::::]]]], [[[[::::pppprrrriiiinnnntttt::::]]]], [[[[::::ppppuuuunnnncccctttt::::]]]], [[[[::::ssssppppaaaacccceeee::::]]]], [[[[::::uuuuppppppppeeeerrrr::::]]]], and [[[[::::xxxxddddiiiiggggiiiitttt::::]]]].... For example, [[[[[[[[::::aaaallllnnnnuuuummmm::::]]]]]]]] means [[[[0000----9999AAAA----ZZZZaaaa----zzzz]]]], except the latter form depends upon the POSIX locale and the ASCII character encoding, whereas the former is independent of locale and character set. (Note that the brackets in these class names are part of the symbolic names, and must be included in addition to the brackets delimiting the bracket list.) Most metacharacters lose their special meaning inside lists. To include a literal ]]]] place it first in the list. Similarly, to include a literal ^^^^ place it anywhere but first. Finally, to include a literal ---- place it last. The period .... matches any single character. The symbol \\\\wwww is a synonym for [[[[[[[[::::aaaallllnnnnuuuummmm::::]]]]]]]] and \\\\WWWW is a synonym for [[[[^^^^[[[[::::aaaallllnnnnuuuummmm]]]]]]]]. The caret ^^^^ and the dollar sign $$$$ are metacharacters that respectively match the empty string at the beginning and end of a line. The symbols \\\\<<<< and \\\\>>>> respectively match the empty string at the beginning and end of a word. The symbol \\\\bbbb matches the empty string at the edge of a word, and \\\\BBBB matches the empty string provided it's _n_o_t at the edge of a Page 5 (printed 4/5/00) GGGGRRRREEEEPPPP((((1111)))) GGGGNNNNUUUU PPPPrrrroooojjjjeeeecccctttt ((((2222000000000000////00002222////22226666)))) GGGGRRRREEEEPPPP((((1111)))) word. A regular expression may be followed by one of several repetition operators: ???? The preceding item is optional and matched at most once. **** The preceding item will be matched zero or more times. ++++ The preceding item will be matched one or more times. {{{{_n}}}} The preceding item is matched exactly _n times. {{{{_n,,,,}}}} The preceding item is matched _n or more times. {{{{_n,,,,_m}}}} The preceding item is matched at least _n times, but not more than _m times. Two regular expressions may be concatenated; the resulting regular expression matches any string formed by concatenating two substrings that respectively match the concatenated subexpressions. Two regular expressions may be joined by the infix operator ||||; the resulting regular expression matches any string matching either subexpression. Repetition takes precedence over concatenation, which in turn takes precedence over alternation. A whole subexpression may be enclosed in parentheses to override these precedence rules. The backreference \\\\_n, where _n is a single digit, matches the substring previously matched by the _nth parenthesized subexpression of the regular expression. In basic regular expressions the metacharacters ????, ++++, {{{{, ||||, ((((, and )))) lose their special meaning; instead use the backslashed versions \\\\????, \\\\++++, \\\\{{{{, \\\\||||, \\\$(((, and \\\$))). Traditional eeeeggggrrrreeeepppp did not support the {{{{ metacharacter, and some eeeeggggrrrreeeepppp implementations support \\\\{{{{ instead, so portable scripts should avoid {{{{ in eeeeggggrrrreeeepppp patterns and should use [[[[{{{{]]]] to match a literal {{{{. GNU eeeeggggrrrreeeepppp attempts to support traditional usage by assuming that {{{{ is not special if it would be the start of an invalid interval specification. For example, the shell command eeeeggggrrrreeeepppp ''''{{{{1111'''' searches for the two-character string {{{{1111 instead of reporting a syntax error in the regular expression. POSIX.2 allows this behavior as an extension, but portable scripts should avoid it. EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT VVVVAAAARRRRIIIIAAAABBBBLLLLEEEESSSS GGGGRRRREEEEPPPP____OOOOPPPPTTTTIIIIOOOONNNNSSSS This variable specifies default options to be placed in Page 6 (printed 4/5/00) GGGGRRRREEEEPPPP((((1111)))) GGGGNNNNUUUU PPPPrrrroooojjjjeeeecccctttt ((((2222000000000000////00002222////22226666)))) GGGGRRRREEEEPPPP((((1111)))) front of any explicit options. For example, if GGGGRRRREEEEPPPP____OOOOPPPPTTTTIIIIOOOONNNNSSSS is ''''--------bbbbiiiinnnnaaaarrrryyyy----ffffiiiilllleeeessss====wwwwiiiitttthhhhoooouuuutttt----mmmmaaaattttcccchhhh --------ddddiiiirrrreeeeccccttttoooorrrriiiieeeessss====sssskkkkiiiipppp'''', ggggrrrreeeepppp behaves as if the two options --------bbbbiiiinnnnaaaarrrryyyy----ffffiiiilllleeeessss====wwwwiiiitttthhhhoooouuuutttt----mmmmaaaattttcccchhhh and --------ddddiiiirrrreeeeccccttttoooorrrriiiieeeessss====sssskkkkiiiipppp had been specified before any explicit options. Option specifications are separated by whitespace. A backslash escapes the next character, so it can be used to specify an option containing whitespace or a backslash. LLLLCCCC____AAAALLLLLLLL, LLLLCCCC____MMMMEEEESSSSSSSSAAAAGGGGEEEESSSS, LLLLAAAANNNNGGGG These variables specify the LLLLCCCC____MMMMEEEESSSSSSSSAAAAGGGGEEEESSSS locale, which determines the language that ggggrrrreeeepppp uses for messages. The locale is determined by the first of these variables that is set. American English is used if none of these environment variables are set, or if the message catalog is not installed, or if ggggrrrreeeepppp was not compiled with national language support (NLS). LLLLCCCC____AAAALLLLLLLL, LLLLCCCC____CCCCTTTTYYYYPPPPEEEE, LLLLAAAANNNNGGGG These variables specify the LLLLCCCC____CCCCTTTTYYYYPPPPEEEE locale, which determines the type of characters, e.g., which characters are whitespace. The locale is determined by the first of these variables that is set. The POSIX locale is used if none of these environment variables are set, or if the locale catalog is not installed, or if ggggrrrreeeepppp was not compiled with national language support (NLS). PPPPOOOOSSSSIIIIXXXXLLLLYYYY____CCCCOOOORRRRRRRREEEECCCCTTTT If set, ggggrrrreeeepppp behaves as POSIX.2 requires; otherwise, ggggrrrreeeepppp behaves more like other GNU programs. POSIX.2 requires that options that follow file names must be treated as file names; by default, such options are permuted to the front of the operand list and are treated as options. Also, POSIX.2 requires that unrecognized options be diagnosed as ``illegal'', but since they are not really against the law the default is to diagnose them as ``invalid''. PPPPOOOOSSSSIIIIXXXXLLLLYYYY____CCCCOOOORRRRRRRREEEECCCCTTTT also disables _____N____GGGGNNNNUUUU____nnnnoooonnnnooooppppttttiiiioooonnnn____aaaarrrrggggvvvv____ffffllllaaaaggggssss____, described below. _____N____GGGGNNNNUUUU____nnnnoooonnnnooooppppttttiiiioooonnnn____aaaarrrrggggvvvv____ffffllllaaaaggggssss____ (Here _N is ggggrrrreeeepppp's numeric process ID.) If the _ith character of this environment variable's value is 1111, do not consider the _ith operand of ggggrrrreeeepppp to be an option, even if it appears to be one. A shell can put this variable in the environment for each command it runs, specifying which operands are the results of file name wildcard expansion and therefore should not be treated as options. This behavior is available only with the GNU C library, and only when PPPPOOOOSSSSIIIIXXXXLLLLYYYY____CCCCOOOORRRRRRRREEEECCCCTTTT is not Page 7 (printed 4/5/00) GGGGRRRREEEEPPPP((((1111)))) GGGGNNNNUUUU PPPPrrrroooojjjjeeeecccctttt ((((2222000000000000////00002222////22226666)))) GGGGRRRREEEEPPPP((((1111)))) set. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS Normally, exit status is 0 if matches were found, and 1 if no matches were found. (The ----vvvv option inverts the sense of the exit status.) Exit status is 2 if there were syntax errors in the pattern, inaccessible input files, or other system errors. BBBBUUUUGGGGSSSS Email bug reports to bbbbuuuugggg----ggggnnnnuuuu----uuuuttttiiiillllssss@@@@ggggnnnnuuuu....oooorrrrgggg. Be sure to include the word ``grep'' somewhere in the ``Subject:'' field. Large repetition counts in the {{{{_m,,,,_n}}}} construct may cause grep to use lots of memory. In addition, certain other obscure regular expressions require exponential time and space, and may cause ggggrrrreeeepppp to run out of memory. Backreferences are very slow, and may require exponential time. Page 8 (printed 4/5/00)